#+TITLE: Guile FFI Notes
#+AUTHOR: Zelphir Kaltstahl
#+EMAIL: zelphirkaltstahl@posteo.de
#+STARTUP: content indent align inlineimages hideblocks entitiesplain nologdone nologreschedule nologredeadline nologrefile
#+TODO: TODO INPROGRESS | DONE
#+DATE: [2021-10-10 Sun]
#+LANGUAGE: English
#+PRIORITIES: A E E

* Guile FFI

For all things FFI in the GNU Guile standard library look at: [[https://www.gnu.org/software/guile/manual/html_node/Foreign-Function-Interface.html]]

What to point at:

#+begin_quote
ffi is pointed at the shared objects

-- lilyp
#+end_quote

* Nyacc FFI helper

Read more about it at: [[https://www.nongnu.org/nyacc/ffi-help.html]].

#+begin_quote
The nyacc ffi-helper is a C parser (and C preprocessor), plus a converter that turns declarations from include files into Guile ffi wrapper code.

-- mwette
#+end_quote

What to point FFI at:

#+begin_quote
nyacc OTOH is pointed at the header files

-- lilyp
#+end_quote

* General notes

** TAR

=libarchive= implements all TAR functions and functions for other archive formats.

Wiki:

#+begin_quote
Most modern tar programs read and write archives in the UStar (Unix Standard TAR[2][10]) format, introduced by the POSIX IEEE P1003.1 standard from 1988.

-- https://en.wikipedia.org/wiki/Tar_%28computing%29#UStar_format
#+end_quote

*** Weblinks

https://wiki.osdev.org/USTAR
https://en.wikipedia.org/wiki/Tar_%28computing%29
https://en.wikipedia.org/wiki/Tar_%28computing%29#UStar_format

** Difficulties

#+begin_quote
difficulties will depend on things like memory management

-- RhodiumToad
#+end_quote
